My company does db level journaling which causes all of "Client submission probe" emails to be journaled. We use Symantec Enterprise Vault to archive all the emails as soon as they arrive in journaling mailbox. I am testing various solutions to prevent these emails from being archived and would like to know what other people have done to address this issue. I've read a few solutions and none of them we can fully implement. 1 - we can't turn off these probe emails due to IT policy, 2 - I can't create a "hard delete" rule as it's only a client side rule, 3 - I have created a rule to move them to Deleted item but those don't empty manually and I don't like have scheduled tasks running when it comes to mailbox management (create a PS script to autoempty the Deleted Items after a period of time). I am considering creating a transport rule that will block those emails from ever arriving at the journaling mailbox but I am yet to test this.

How have you addressed this problem?

PS. I created a transport rule but I don't think it's able to catch messages that are placed into the journaling mailbox.

• Edited by Ziv Rivkis 8 hours 33 minutes ago spelling

Hi Rivkis,

Thank you for your question.

We would like to know more details about Client submission probe.

By my understanding, you want to block journaling which send from client submission probe, we could compare the client submission probe journaling with generally email journaling, if we find any differences, then create transport rule to block it. Because journaling has database level and mailbox level, database level can exclude the specific mailbox, but mailbox level cannot exclude the specific email for journaling. If I misunderstand, please be free to let me know.

If there are any questions regarding this issue, please be free to let me know. 

Best Regard,

Jim